Reducing network latency

ABSTRACT

A method of transmitting data for use at a data processing system and network interface device, the data processing system being coupled to a network by the network interface device, the method comprising: forming a message template in accordance with a predetermined set of network protocols, the message template including at least in part one or more protocol headers; forming an application layer message in one or more parts; updating the message template with the parts of the application layer message; processing the message template in accordance with the predetermined set of network protocols so as to complete the protocol headers; and causing the network interface device to transmit the completed message over the network.

BACKGROUND

This invention relates to low-latency methods for transmitting data at adata processing system.

It is generally desirable to minimise the latency associated withsending messages over a network between applications. This enables areceiving application to receive a message the minimum possible timeafter the sending application forms the message.

It is especially important to minimise the latency over networks thatconnect high performance computing devices, or computing devices thatmust react as quickly as possible to incoming data in order to gain acommercial advantage, such as electronic trading devices. In electronicmarkets, messages sent over networks are used to submit orders andquotes to exchanges and it is often of considerable benefit for acomputing system to be able to respond to external stimuli and submitorders and quotes ahead of competitors.

Applications running at computing devices on a network typicallycommunicate over the network using an application-level protocol (suchas HTTP or the Financial Information Exchange or FIX protocol) thatdefine a series of structured messages. In order to form each message,the data for transmission must be processed in accordance with theapplication-level protocol (as well as lower layer protocols, such asEthernet) in order to form a completed message that is ready fortransmission over the network. Typically this protocol processing takesthe form of generating headers and calculating error checks (such asCRCs). Such protocol processing can introduce significant latency intothe transmission of data since in conventional data transmission systemsa network protocol stack must wait for all of the data that is to form amessage to be available before commencing protocol processing. This cansignificantly extend the time elapsed between an application determiningthat a message is to be sent and that message actually being transmittedonto the wire.

Other causes of transmission latency in conventional systems include therestriction for connection-oriented protocols (such as TCP) that onlythe protocol stack that negotiated the connection can transmit over theconnection. Often such a protocol stack is supported at a host kernel,which does not present a low latency transmission path to applicationsof the system. Additionally, a modern processor can introducesignificant latency if the state and instructions required by atransmission process is not available in cache at the processor.

There is therefore a need for improved methods for transmitting data ata data processing system that reduce the latency associated with messagetransmission.

SUMMARY

Roughly described, according to a first aspect of the first inventionthere is provided a method of transmitting data for use at a dataprocessing system supporting an application, a software interface and anetwork protocol stack, the data processing system being coupled to anetwork by a network interface device, the method comprising: theapplication: forming one or more parts of a message for transmission;causing a message template to be generated by means of a first requestto the software interface; the software interface: on receiving thefirst request, causing the network protocol stack to include said one ormore parts of the message for transmission in the message template and,in accordance with a predetermined set of protocols, form at least inpart one or more protocol headers for the message for transmission; andsubsequently: forming one or more further parts of the message fortransmission; causing the network protocol stack to include the one ormore further parts of the message in the message template and, oncompletion of the message for transmission, process the message inaccordance with the predetermined set of protocols so as to complete theprotocol headers; and causing the network interface device to transmitthe completed message over the network.

Suitably the step of forming one or more further parts of the messagefor transmission is performed by the application and the step of causingthe network protocol stack to include the one or more further parts ofthe message in the message template is effected by means of a secondrequest made by the application to the software interface. Suitably theapplication makes a series of second requests to the software interface,each second request being made on one or more further parts of themessage for transmission becoming available to the application. Thefinal request of the second request type in the series preferablycompletes the message for transmission, causing the network protocolstack to process the message in accordance with the predetermined set ofprotocols so as to complete the protocol headers and the networkprotocol stack to transmit the completed message.

Preferably the network protocol stack comprises at least two parts: afirst part supported at the data processing system and a second partsupported at the network interface device; the first part beingconfigured to perform the step of forming at least in part one or moreprotocol headers of the message for transmission, and the second partbeing configured to perform the step of processing the message so as tocomplete the protocol headers. Preferably the step of forming the one ormore further parts of the message for transmission is performed at adata processing engine of the network interface device. Preferably thestep of causing the second part of the network protocol stack to processthe message so as to complete the protocol headers is performed inresponse to completing formation of the one or more further parts of themessage for transmission.

Preferably the first part of the network protocol stack is a user-levelprotocol stack.

Suitably at least part of the message template is held at the networkinterface device.

Preferably the first request includes memory references to the one ormore parts of a message for transmission.

The method suitably further comprises, subsequent to the networkprotocol stack including said one or more parts of the message fortransmission in the message template, the network protocol stackperforming segmentation of the message template in accordance with apredetermined transport protocol such that the one or more parts of themessage are transmitted over the network in one or more message segmentsby the network interface device. The method suitably further comprises,subsequent to the network protocol stack including said one or morefurther parts of the message for transmission in the message template,the network protocol stack causing those segments of the messagetemplate that correspond to the further parts of the message fortransmission to be transmitted over the network by the network interfacedevice. Preferably the step of the network protocol stack causing thosesegments of the message template that correspond to the further parts ofthe message for transmission to be transmitted over the networkcompletes the step of the network interface device transmitting themessage over the network.

The predetermined transport protocol could be the transmission controlprotocol.

Suitably the transport protocol is configured such that a messagesegment can carry a plurality of parts of the message for transmissionthat are not contiguous in the message for transmission. Suitably amessage segment can include one or more header fields that determine thelogical position within the message for transmission of the parts of themessage in the message segment. Suitably the one or more header fieldsare formed in a TCP header option. Preferably all of the one or moreparts of the message are transmitted over the network in a singlemessage segment by the network interface device.

Suitably at least part of the message template is stored at the networkinterface device, that part of the message template stored at thenetwork interface device including the one or more parts of a messagefor transmission.

Preferably the step of the network protocol stack including the one ormore further parts of the message in the message template comprisestransferring the one or more further parts of the message into themessage template using one or more programmed I/O instructions.Alternatively the step of the network protocol stack including the oneor more further parts of the message in the message template comprises:for those further parts of the message that are below a predeterminedlength, transferring the one or more further parts of the message intothe message template using one or more programmed I/O instructions; andfor those further parts of the message that are above the predeterminedlength, transferring the one or more further parts of the message intothe message template by means of direct memory access by the networkinterface device.

Preferably the software interface is configured to provide a dummytransmission function by means of which an application can cause thenetwork protocol stack to process the message template in accordancewith the predetermined set of protocols as if for transmission by thenetwork interface device, the method further comprising, prior to thestep of the network interface device transmitting the message over thenetwork, the application periodically calling the dummy transmissionfunction so as to cause the network protocol stack to process themessage template in accordance with the predetermined set of protocolswithout causing the network interface device to transmit the processedmessage template over the network.

Suitably the step of calling the dummy transmission function comprises,prior to the network protocol stack processing the message template inaccordance with the predetermined set of protocols, the network protocolstack padding the message template with data so as to fill the missingparts of the message for transmission.

The message template could be a logical expression of the message fortransmission.

Preferably the software interface is an application programminginterface.

Preferably at least part of the network protocol stack is at user level.

According to a second aspect of the first invention there is provided adata processing system coupled to a network by a network interfacedevice and comprising: an application configured to form one or moreparts of a message for transmission; a network protocol stack configuredto process messages for transmission in accordance with a predeterminedset of network protocols; a software interface configured to, inresponse to a first request, cause the network protocol stack to form atleast in part one or more protocol headers of a message fortransmission; wherein the application is configured to, on forming oneor more parts of a message for transmission, make a first request to thesoftware interface so as to cause the network protocol stack to form amessage template comprising at least in part one or more protocolheaders of a message for transmission and the one or more parts of themessage for transmission; and subsequently: the network protocol stackbeing configured to, on one or more further parts of the message fortransmission being formed, include the one or more further parts of themessage in the message template and, on completion of the message fortransmission, process the message in accordance with the predeterminedset of protocols so as to complete the protocol headers and cause thenetwork interface device to transmit the completed message over thenetwork.

Suitably the application is configured to form the one or more furtherparts of the message for transmission and to cause the network protocolstack to include the one or more further parts of the message in themessage template by means of a second request to the software interface.

Preferably the one or more further parts of the message for transmissionare formed at the network interface device at a data processing engineof the network interface, and the network protocol stack comprises atleast two parts: a first part supported at the data processing systemand a second part supported at the network interface device; the firstpart being configured to perform the step of forming at least in partone or more protocol headers of the message for transmission, and thesecond part being configured to perform the step of processing themessage so as to complete the protocol headers.

According to a third aspect of the first invention there is provided amethod of transmitting data for use at a data processing system andnetwork interface device, the data processing system being coupled to anetwork by the network interface device, the method comprising: forminga message template in accordance with a predetermined set of networkprotocols, the message template including at least in part one or moreprotocol headers; forming an application layer message in one or moreparts; updating the message template with the parts of the applicationlayer message; processing the message template in accordance with thepredetermined set of network protocols so as to complete the protocolheaders; and causing the network interface device to transmit thecompleted message over the network.

Preferably the step of forming a message template is performed at anetwork protocol stack supported at the data processing system. The stepof forming an application layer message could be performed by one of anapplication supported at the data processing system, and a dataprocessing engine of the network interface device or other peripheraldevice of the data processing system. Preferably the processing step isperformed at a packet processing engine supported at the networkinterface device.

According to a fourth aspect of the first invention there is provided adata processing system coupled to a network, the data processing systemcomprising: a network protocol stack configured to, in accordance with apredetermined set of network protocols, form a message templateincluding at least in part one or more protocol headers; and a messageforming engine configured to form an application layer message in one ormore parts and, on the formation of each of those parts, cause therespective part of the message to be applied to the message template;wherein the network protocol stack is further configured to, on theapplication layer message being completed, process the message templatein accordance with the predetermined set of network protocols so as tocomplete the protocol headers and cause the completed message to betransmitted over the network.

Preferably the network protocol stack is supported at a networkinterface device arranged to couple the data processing system to thenetwork. The message forming engine could be one or both of anapplication supported at the data processing system or a data processingengine at a network interface device arranged to couple the dataprocessing system to the network.

According to a first aspect of the second invention there is provided amethod of transmitting data in accordance with a connection-orientednetwork protocol, the method being for use at a data processing systemcoupled to a network and supporting first and second packet processingengines, the method comprising: initiating a connection at the firstpacket processing engine; the first packet processing engine passingfirst network protocol state to the second packet processing enginesufficient to permit the second packet processing engine to transmit aspecified amount of data over the connection; forming application layerdata for transmission; and the second packet processing engineperforming packet processing of the application layer data in dependenceon the first network protocol state so as to form one or more networkmessages and causing transmission of one or more network messages overthe connection.

Preferably the data processing system is coupled to the network by anetwork interface device and the second packet processing engine issupported at the network interface device.

Preferably the step of forming application layer data for transmissionis performed at a data processing engine of the network interfacedevice. Alternatively the step of forming application layer data fortransmission is performed at an application supported at the dataprocessing system. Alternatively the step of forming application layerdata for transmission is performed at a data processing engine supportedat a peripheral device of the system.

Preferably the passing step is performed in response to a request madeby the second packet processing engine.

The first network protocol state could be a message template includingat least in part one or more protocol headers for a network message.

Preferably the first packet processing engine performs processing ofnetwork messages received over the connection. Preferably the firstpacket processing engine is a software network protocol stack supportedat kernel or user level at the data processing system. Preferably thesecond packet processing engine is configured to perform packetprocessing of the application layer data using an FPGA, ASIC, dedicatedhardware, or embedded software.

The method could further comprise, subsequent to the passing step, thefirst packet processing engine signalling to the second packetprocessing engine so as to cause the second packet processing engine toreturn control of the connection to the first packet processing engine.The method could further comprise, in response to the signalling, thesecond packet processing engine completing any pending transmissionoperations over the connection and passing second network protocol stateto the first packet processing engine so as to return control of theconnection to the first packet processing engine.

The method preferably further comprises, on the amount of datatransmitted over the connection becoming within a predetermined amountof the specified amount of data, the second packet processing enginerequesting updated network protocol state from the first packetprocessing engine and, in response to the request, the first packetprocessing engine passing updated network protocol state to the secondpacket processing engine. The method preferably further comprises:forming additional application layer data for transmission; and thesecond packet processing engine performing packet processing of theadditional application layer data in dependence on the updated networkprotocol state so as to form one or more network messages and causingtransmission of the one or more network messages over the connection.

Preferably the steps of forming the application layer data andperforming packet processing comprise: forming one or more first partsof the application layer data; the second packet processing engineprocessing the one or more parts of the application layer data independence on the first network protocol state so as to form a messagetemplate including at least in part one or more protocol headers; andsubsequently: forming one or more additional parts of the applicationlayer data; and updating the message template with the one or moreadditional parts of the application layer data so as to complete themessage template and processing the message template so as to completethe protocol headers.

Preferably the method further comprises, once the specified amount ofdata has been transmitted over the connection, the second packetprocessing engine returning control of the connection to the firstpacket processing engine.

Suitably the connection-oriented network protocol is TCP.

In any aspect of any of the inventions disclosed herein a dataprocessing engine could be an FPGA, ASIC, dedicated hardware, orembedded software.

According to a second aspect of the second invention there is provided adata processing system coupled to a network, the data processing systemcomprising: a message forming engine operable to form application layerdata for transmission over the network in accordance with aconnection-oriented network protocol; a first packet processing engineoperable to initiate a connection in accordance with theconnection-oriented network protocol; a second packet processing engineoperable to perform packet processing of application layer data so as toform one or more network messages in accordance with theconnection-oriented network protocol; wherein the first packetprocessing engine is configured to, subsequent to initiating theconnection, pass first network protocol state to the second packetprocessing engine sufficient to permit the second packet processingengine to transmit a specified amount of data over the connection, andthe second packet processing engine is configured to, on receivingapplication layer data from the message forming engine, perform packetprocessing of the application layer data in dependence on the firstnetwork protocol state so as to form one or more network messages andcause transmission of one or more network messages over the connection.

According to a first aspect of a third invention there is provided amethod for minimising execution latency of a communication processprovided for execution at a data processing system, the data processingsystem being coupled to a network and supporting a software interface,an application and a network protocol stack providing a communicationprocess, and the method comprising the application periodically making acall to a dummy communication function of the software interface so asto cause the network protocol stack to perform the communication processwithout communicating data over the network.

Preferably the software interface provides a communication functioncorresponding to the dummy communication function and the method furthercomprises the application subsequently making a call to thecommunication function in respect of a network message so as to causethe network protocol stack to perform the communication process andcommunicate the network message over the network. Suitably the dummycommunication function and the corresponding communication function areone and the same, and the dummy communication function is identified bymeans of a flag of the communication function.

Suitably the communication process is a transmit process and the step ofmaking a call to a communication function comprises the applicationperiodically making a call to a dummy transmit function of the softwareinterface so as to cause the network protocol stack to perform thetransmit process without transmitting data over the network.

Suitably the dummy transmit function is called in respect of a partialmessage held at a transmit buffer of the data processing system.

Suitably the communication process is a receive process and the step ofmaking a call to a communication function comprises the applicationperiodically making a call to a dummy receive function of the softwareinterface so as to cause the network protocol stack to perform thereceive process of the network protocol stack without receiving dataover the network.

DESCRIPTION OF THE DRAWINGS

The present invention will now be described by way of example withreference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram of a data processing system and networkinterface device configured in accordance with the present invention.

FIG. 2 is a flow chart illustrating data transmission in accordance withthe present invention.

FIG. 3 shows a general overview of the interaction of the variouscomponents of FIG. 1.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled inthe art to make and use the inventions, and is provided in the contextof a particular application. Various modifications to the disclosedembodiments will be readily apparent to those skilled in the art.

The general principles defined herein may be applied to otherembodiments and applications without departing from the spirit and scopeof the present inventions. Thus, the present inventions are not intendedto be limited to the embodiments shown, but is to be accorded the widestscope consistent with the principles and features disclosed herein.

The present inventions relate to the transmission of data over a networkbetween data processing systems. A data processing system could be anykind of computing device, such as a server, personal computer orhandheld device. The present inventions are described herein by way ofexample with reference to networks that operate TCP/IP over Ethernet,but it will be appreciated by the skilled person that the presentinvention is not so limited and could be implemented with any kind ofnetwork (wired or wireless) and set of network protocols. The presentinventions are particularly suitable for use at a data processing systemand network interface device (NIC)_configured such that at least part ofthe protocol processing of data packets for transmission is performed atthe NIC. Thus, at least some of the network protocol stack can besupported at the NIC, with one or more network protocols being offloadedin part or in full to the NIC to be performed in hardware at the NIC.

The present inventions address the latencies introduced in thetransmission of data packets or messages over a network when the datafor some parts of a network message are not immediately known to theentity that forms the application-layer message and requests the datatransmission operation. Often, data that is to constitute some parts ofa message are immediately known to an application on determining that amessage is to be sent, whilst data for other parts of the message arenot known until just before the message is transmitted over the network.In conventional transmission systems, the network stack waits for all ofthe data for the message to become available prior to performingprotocol processing and transmitting the message.

The first of the inventions provides a mechanism by which a networkmessage can be incrementally constructed by one or more network protocolstacks and one or more entities forming application layer data. This canbe achieved through the provision of an interface by which anapplication supported at a data processing system can provide data fortransmission to a network stack as and when the data becomes available,allowing the network stack to perform any possible protocol processingand minimising the latency caused by data that is available only at thelast moment. The second of the inventions provides a mechanism by whicha stream of a connection-oriented protocol can be handed between networkprotocol stacks. This allows a host to manage the protocol streams butpermit another network protocol stack to perform at least sometransmission operations at low latency. It is intended that the firstand second inventions can be used together. Thus the first inventionalong with any of its optional features can be implemented with thesecond invention along with any of its optional features. The first andsecond inventions described below are therefore not mutually exclusiveand disclosure is made of the combination of the first invention in anyof its embodiments and the second invention in any of its embodiments.

A schematic diagram of a system 100 configured in accordance with thepresent inventions is shown in FIG. 1. Data processing system 101supports an operating system 103 and an application 104 that is operableto communicate over network 107 by means of network interface device orNIC 102 and network protocol stack 105. The network protocol stack isillustrated as a logical block in the figure and all or part of thestack could be supported at kernel, user-level, or at the networkinterface device 102. All or part of the protocols of the network stackcould be performed at a packet processing engine 108 of the networkinterface device itself. The network interface device could optionallyalso support a message generating entity 109 configured to generateapplication-layer network messages in an analogous manner to the way inwhich application 104 might form messages for transmission over thenetwork. The network interface device could be supported at the dataprocessing system; for example, it could be provided at the mainboard ofthe data processing system.

The first invention will now be described by way of example withreference to FIG. 1.

The first invention provides a mechanism by which a network message canbe incrementally constructed by one or more network protocol stacks andone or more entities forming application layer data. On a request beingmade to transmit a network message (for example, by means of a call froman application to a socket API provided by the operating system), anetwork protocol stack of system 100 is configured to generate a messagetemplate for the network message in accordance with a predetermined setof network protocols such that the message template includes at least inpart one or more protocol headers for the message. If, at the time thetransmit request is made, any data for transmission is available fromone or more entities of the system that are arranged to form applicationlayer data, the network protocol stack also includes that data in themessage template.

Thus, a message template that can include parts of the application-layermessage for transmission is generated whilst the remainder of themessage is formed. As further parts of the message become available, themessage template can be updated with those parts of the message. Onceall of the message is available, a network protocol stack of the systemcompletes protocol processing of the data packet so as to complete itsprotocol headers and the packet is transmitted over the network by thenetwork interface device. The message template is a logical constructthat includes the known parts of the message and headers (and/or otherdata) generated by the protocol stack. The data defining a messagetemplate could be included by means of one or more memory references(e.g. to the known parts of the message). The message template could becontiguously defined in memory such as a transmit buffer.

Any of application 104, operating system 103, message generating entity109 at the NIC, or a message generating entity at another peripheraldevice of system 100 could be an entity forming application layer data.Either the kernel or user-level network stack 105, or packet processingengine 108 at the NIC represent network protocol stacks. Sometimes it isadvantageous for one entity forming application layer data to requesttransmission of a message and optionally provide some of the messagedata, and for another entity forming application layer data to completethe message. The first invention can be performed and a network datapacket built up incrementally irrespective of where the protocolprocessing is performed and where the message data is formed.

Similarly, it can be advantageous for one network protocol stack tocommence packet processing and for another network protocol stack tocomplete packet processing. For example, application 104 at the dataprocessing system could request transmission of a network message andprovide some of the data for that message before passing over to networkgenerating entity 109 at the NIC, which generates the remainder of themessage. The message template in this example be generated at a userlevel network stack 105 before passing control of the remainder of theprocessing of the network message to packet processing engine 108 at theNIC. This example ensures that the final parts of a message and thecompletion of protocol processing of the network message is performedwith low latency at the NIC.

According to a preferred embodiment of the first invention, a softwareinterface 106 is provided by means of which application 104 at the hostdata processing system can request that data for transmission is formedinto a message by network stack 105 and transmitted over network 107 bymeans of NIC 102. Preferably, software interface 106 is an applicationprogramming interface or API.

A flow chart illustrating data transmission in accordance with thepresent invention is shown in FIG. 2. On determining that data is to besent over a network to a remote endpoint, at step 201 application 104forms those parts of the message that are known to the application andat step 202 requests by means of software interface 106 that a messagetemplate is created. The application passes a reference to the dataconstituting the known parts of the message in its request 202,typically a memory reference to the location of the those message partsin an application buffer. In response to the request the softwareinterface causes network protocol stack 105 to create a message templateat step 203 including those known parts of the message that were formedby the application at step 201.

Preferably the network stack populates the message template with data bycopying the data known to the application from the application's buffersto the transmit buffer holding the message template, with the data beingwritten to the template at the position that data is to have in thecompleted message. Alternatively, references to the known applicationdata are included in the message template so as to allow the fullmessage to be logically read from the transmit buffer when the messageis completed. The message template represents the completed message onceit includes all data for transmission from the application and allprotocol processing has been completed by the protocol stack (e.g. toform the appropriate headers for the message). Protocol processing maybe performed in software at the data processing system, or in hardwareat the network interface device. Typically some protocols are completedon-the-fly by the network interface device as the message traverses theNIC—for example, the calculation of CRC check data for Ethernet datapackets. A completed message is transmitted over the network at step205.

Software interface 106 is configured so as to provide a mechanism bywhich an application can provide further parts of the message to thenetwork stack as they become known to the application. This is shown bymessage update step 204 in FIG. 2, which comprises the applicationmaking a request to the software interface by means of which it passesone or more references to the data that is to be included as furtherparts of the message. In response to the message update request,software interface 106 causes the network protocol stack to include thenewly-available data into the message template. Message update step 204can be performed as many times as is necessary to complete the messagetemplate, as indicated by return arrow 206.

A general overview of the interaction of the various components of FIG.1 is shown in FIG. 3. Application 104 is configured to access softwareinterface 106 by means of a set of commands or requests 301. Preferablysoftware interface 106 is an application programming interface (API)with requests 301 being calls to the API. As indicated by arrow 302, thesoftware interface is configured to cause network protocol stack 105 toinclude data held at the application buffer(s) 305 of application 104into message template 307 held in transmit buffer 306. Arrow 303indicates the transfer of data or references to data from theapplication buffers into the message template.

Additionally, network stack 105 is configured to perform on the data ofthe message template the appropriate possible protocol processing, suchas the formation of protocol headers and footers. For example, even whennone or only some of the data of the message is known, for manyprotocols it is possible to form the source and destination addressesand specify certain header options, such as packet length and sequencenumber. Performing this processing whilst the application is waiting forsome of the packet data to become available minimises the latencyassociated with transmitting the message since the amount of protocolprocessing to be performed once all of the message data is known isreduced and hence the time between the last of the message data beingavailable and the point at which the message is actually transmitted isreduced.

Often most of the payload data of a data packet will be available to anapplication, but some parts of the payload data will only be availableimmediately prior to the transmission of the data packet over a network.This is typically because the application is performing calculations todetermine those parts of the message data. For example, in the case inwhich the application is an electronic trading application, theapplication might only determine the price, quantity or symbol for atrade at the last moment before an electronic trading message is sent.However, it is vitally important that the latency of the trade is assmall as possible and the present invention achieves this by arrangingthat as much of the protocol processing of the data packet as possibleis performed prior to the final parts of the message being available.

The message template may be held in transmit buffers at the dataprocessing system or at the NIC, or the logical message template couldbe held in part in memory at the data processing system and in part atmemory at the NIC. If the message template 307 is held at the dataprocessing system, the network interface device 102 is preferablyconfigured to have direct memory access (DMA) to transmit buffer(s) 306and hence reads completed messages from the transmit buffers of the dataprocessing system by means of DMA (indicated by arrow 304 in FIG. 3). Ifthe message template 307 is held in transmit buffer(s) 306 at the NIC,the NIC 102 can access (arrow 304) the message template directly.Arranging that the message template is held at the NIC, with at leastsome further protocol processing being performed at the NIC can help tofurther minimise the latency of transmission operations.

Note that network protocol stack 105 is illustrated in the figures as asingle entity but may in fact comprise one or more software entitiesthat could be located at kernel or user level at the data processingsystem. The stack 105 could be a user-level protocol stack configured toperform protocol processing in the context of user-level software so asto minimise context switches into the kernel. Further parts of the totalnetwork protocol stack could be performed at the network interfacedevice 102. For example, in the case of a network interface device thatsupports TCP offload, the majority of TCP protocol processing would beperformed at the network interface device.

Protocol processing could be performed at NIC 102 at a packet processingengine 109, which could be, for example, an FPGA, ASIC, embeddedsoftware or a hardware protocol processing engine configured to performdedicated processing according to one or more network protocols. Incertain configurations, it can be advantageous for a data processingsystem and NIC to support multiple entities capable of performingprotocol processing. For example, a data processing system might supportboth kernel and user-level protocol stacks, and at least part of a stacksupported at the data processing system could also be supported at theNIC. The data processing system would typically be configured to selectthe appropriate stack in dependence on the message type, networkconditions, or other factors.

Preferably, the initial protocol processing associated with forming themessage template at step 203 is performed in software at the dataprocessing system and subsequent protocol processing associated withmessage update step 204 is performed at NIC 102. This can havesignificant advantages when the missing parts of the message fortransmission are provided as a result of processing performed at theNIC.

For example, consider the situation in which data processing system 101and NIC 102 form an electronic trading platform whose operation will nowbe described with respect to the figures. At step 201, the electronictrading software determines that a trade is to be placed at anelectronic exchange accessible over network 107 and forms data fortransmission in a bid message to the electronic exchange. At step 202,the trading software requests by means of interface 106 that a messagetemplate be created and that protocol processing is initiated at asoftware protocol stack of the data processing system. In response,interface 106 causes the software protocol stack to commence processingof the message and generate the message template in a buffer memory atthe NIC.

In the present example, most of the data for transmission is known tothe application at the point at which creation of the message templateis requested, with the missing parts of the message being determined atthe NIC by means of trading algorithms running at the NIC at a messageforming entity 108—such as at a dedicated FPGA or ASIC, or by means ofsoftware running at a processor supported at the NIC. This allows thesoftware protocol stack to substantially form the message template,leaving the NIC to add the results of its processing and complete theheaders immediately prior to transmitting the message over the networkfrom its buffer to the electronic exchange. By locating the finalprocessing of the message as close as possible to the network at theNIC, latency is minimised.

Under the control of the trading software 104, the trading algorithmsrunning at the NIC determine the data for the missing parts of themessage template whilst the protocol processing of step 203 isperformed. As soon as the parameters of the trade that represent thefinal parts of the message have been determined by the algorithms, themissing parts of the message are at step 204 included in the messagetemplate by the NIC and the network protocol stack at the NIC (packetprocessing engine 109) completes protocol processing of the data packetbefore at step 205 transmitting the message over the network to theelectronic exchange. Preferably the processes running at the NIC causethe network protocol stack to complete protocol processing of themessage. Preferably the processes are executed at one or more FPGAprocessors of the NIC, the one or more processors optionally including amemory at which the message template is stored.

Typically the trade message would be formed in accordance with the FIXapplication layer protocol over TCP/IP and Ethernet, with the tradingsoftware forming a message in accordance with the FIX protocol and thelower layer protocol stacks being generated at the software stack (whichcould be at user level) of the data processing system. This would leavethe NIC to complete the payload data and message headers in accordancewith the appropriate protocols once the trading algorithms at the NICdetermine the parameters of the bid (e.g. number of stocks, stocksymbol, etc.).

Three transmission mechanisms for use in accordance with the firstinvention will now be described.

A first transmission mechanism can be used with messaging protocols thatsupport segmentation, such as the Transmission Control Protocol (TCP)which will now be discussed by way of example. TCP includes asegmentation algorithm that allows a stream of messages to be split intomultiple segments, each of which includes a sequence number so that thereceiver can reassemble the message stream even when segments arrive outof order. In this embodiment, the network protocol stack is configuredto cause the network interface device to transmit at least some of theknown parts of a message prior to the message template being completed.This is achieved by configuring the network protocol stack to send theknown parts of a message template as TCP segments, with subsequent partsof the message being transmitted as further TCP segments as they becomeknown.

For example, for a message of total length 30 bytes, with 2 bytesinitially unknown at offset 10 bytes, the following TCP segments wouldbe initially transmitted:

-   -   tcp-seq-1: seq=0, len=10    -   tcp-seg-2: seq=12, len=18

On receiving these segments, the receiving data processing system candeliver the first 10 bytes of the message to the receiving applicationbut not any more since it does not yet have the data at sequenceposition 10. Later, when the missing 2 bytes are known, the followingTCP segment would be transmitted:

-   -   tcp-seg-3: seq=10, len=2

The receiving data processing system can then deliver the remaining 20bytes of the message to the receiving application.

The protocol processing stack is configured to perform segmentation ofthe incomplete message template by forming each contiguous known part ofthe message into a message segment and passing the segment to thenetwork interface device for transmission. The protocol processing stackcould be configured to only form a message segment for contiguous partsof the message that exceed a predetermined length so as to avoid theoverhead associated with sending many small data packets. Note that themessage template and message segment(s) need not be a contiguouslystored at a transmit buffer and could be logically represented at atransmit buffer such that it is not necessary to duplicate known partsof the message data in memory—one or both of the message template and amessage segment could refer to the location of the message data held inthe transmit buffer.

This embodiment is of particular benefit if the known parts of themessage are large and the updates are small, since the latency criticalstep of forming and sending the last parts of the segmented messageinvolves sending one (or sometimes a small number of) small messagesegment(s).

However, there are problems with using the TCP protocol in this manner:Each TCP segment can only contain a subset of the message that iscontiguous in the sequence space of the message stream. Hence in theabove example, two segments were needed to transfer only 28 bytes, whichis highly inefficient. This is particularly a problem if a messagetemplate is completed by multiple discrete message parts that requiremultiple message segments to be transmitted in order to complete thetransfer of the message data to the receiving data processing systembecause the formation and transmission of the last message segments iscritical to the overall latency of the message transmission operation.

The technique can only be used if the size of the unknown segments ofdata are known in advance because it is necessary to know where eachmessage part is located in the sequence space.The receiving TCP implementation receives the arriving updates out oforder and therefore will respond to such message segments with an ACKmessage. This can increase the latency of message reception.

In a second transmission mechanism it is therefore proposed that the TCPprotocol is extended or replaced with a new transport protocol thatallows multiple message segments to be delivered in a singlemulti-segment network message. This can be achieved by defining in theprotocol a multi-segment message format arranged to carry multiplesegments of a message as a contiguous data payload and header fieldsthat specify the how the contiguous data payload should be split up intoits constituent message segments at the receiving data processingsystem. For example, by specifying in header fields the byte offsetwithin the parent message and length of each message segment in thepayload, the message segments can be extracted from the payload of themulti-segment message and reassembled to form the parent message. Themessage segments forming the payload of the multi-segment message couldbe separated by markers delineating the message segments; these markerscould be headers carrying the byte offset and optionally lengthinformation of the respective segment in the parent message.

The TCP protocol can be extended to support multiple message segments ineach TCP segment by defining a new TCP header option type to describethe layout of the message segments.

For small messages, the cost of segmentation and reassembly in order totransfer known parts of a message in advance can outweigh the benefits.A third transmission mechanism proposes an alternative strategy in whichknown parts of a message are transferred to buffers at a networkinterface device in advance of those parts of a message not yetavailable to an application. In this embodiment, transmit buffer 306 islocated in memory at the network interface device such that the messagetemplate is formed at a network interface device buffer and data fortransmission is copied into the message template at the NIC inaccordance with steps 203 and 204 of FIG. 2. This ensures that as muchdata as possible is held as close as possible to the NIC at the pointwhen the last of the message data becomes available.

Message data constituting the parts of the message to be held in themessage template can be transferred to the NIC 102 using programmed I/O(PIO) instructions or direct memory access (DMA) by the NIC to buffersheld at the data processing system (these buffers could includeapplication buffer 305, or be an intermediate buffer supported by thenetwork protocol stack). Preferably message update step 204 in FIG. 2 isperformed using PIO instructions to transfer newly-available messageparts into the message template, with the host CPU of the dataprocessing system performing the transfer. This has lower latency thanDMA when small amounts of data are transferred. The initial transfer ofdata at step 203 from the application buffer to the transmit buffer canbe performed by DMA.

Most preferably, the decision as to whether to perform message updatestep 204 by PIO or DMA transfer is made dynamically in dependence on thesize of the message part being transferred, with messages below apredetermined threshold size being transmitted using PIO and messagesabove that threshold being transmitted using DMA.

The second of the inventions will now be described, which provides amechanism by which a stream of a connection-oriented protocol can behanded between network protocol stacks.

In general it is not possible for more than one stack to transmitmessages over a given connection of a connection-oriented networkprotocol such as TCP. In order to maintain the order of messages over aconnection under varying network conditions, the state information (suchas sequence number and receive window parameters) associated with thatconnection is required and that state information resides with theprotocol stack that established the connection.

This invention provides a mechanism by which one network stack can handover the ability to transmit over a connection to another network stackfor a limited period. This will be illustrated by way of example withreference to the system 100 of FIG. 1. Consider a first packetprocessing engine (network stack 105 at data processing system 101) thathas established a TCP connection over network 107 and a second packetprocessing engine (network stack 109 at network interface device 102)that wishes to transmit over that connection. In accordance with theinvention, network stack 105 passes network protocol state to the NICnetwork stack 109 that is sufficient to allow the second packetprocessing engine to transmit a specified amount of data over theconnection. This state can include one or more sequence numbers,congestion window and/or receive window parameters, network addressesand port numbers. By transmitting this state to network stack 109,network stack 105 passes permission to the network stack 109 to transmitdata over the network.

Typically the state includes at least the current sequence number and aparameter identifying the receive window remaining This allows networkstack 109 to start transmitting data packets over the connection untilthe remaining receive window is used up, at which point network stack109 returns control to the parent network stack 105. Note that theconnection state itself need not be copied between the network stacksand the passing of connection state to network stack 109 could beachieved by passing one or more memory references to the state or a copyof the state held in memory at the data processing system.

Most generally, this invention provides a mechanism by which one networkstack can hand over the ability to transmit over a connection to anothernetwork stack irrespective of the locations of those network stacks:either one could be at the kernel of operating system 103, supported atuser level of the data processing system, at packet processing engine108 of NIC 102, or at another peripheral device of the system.

Application layer data for transmission over the connection could beformed at any point in system 100: at the kernel of operating system103, at application 104, at message forming entity 109 of NIC 102, or atanother peripheral device of the system. Application layer data fortransmission over the connection by means of the slave network stack(e.g. 109 in the above example) is provided to the slave network stackand the slave network stack is configured to process the applicationlayer message in dependence on the received state so as to prepare themessage for transmission over the connection by the NIC.

The second invention is particularly advantageous if the message formingentity is close to the slave network stack so as to minimise the latencybetween the application layer message being formed and the resultingdata packet being sent over the connection. Most preferably, the slavenetwork stack is packet processing engine 108 and the message formingentity 109 is located at the NIC. This arrangement is particularlyeffective at minimising the latency of transmission because theformation of application layer messages and the processing of thosemessages into data packets for transmission over the connection isperformed as close as possible at the NIC that effects the transmissionof the data packets over the wire. Furthermore, this mechanism can avoidimplementing the entirety of the connection-oriented protocol inhardware at a NIC, which would be very complex and requires significantprocessing and memory resources at the NIC.

Preferably the parent network stack maintains control of the receivepath of the connection.

Once the slave network stack has transmitted its allowance of data overthe connection, the slave stack returns control to the parent stack andoptionally requests permission to transmit additional data over theconnection. Alternatively, such permission could be requested on behalfof the slave stack—for example, by an application 104 at the dataprocessing system. It is also preferable if the parent stack can directthe slave stack to return control to the parent stack at any moment soas to allow the parent stack to perform its own transmissionoperations—for example, to transmit messages required to maintain theconnection.

To give a particular example, data processing system 101 might supportan electronic trading application 104 that is configured to make use ofa set of trading algorithms arranged to execute at an FPGA 109 of NIC102. On identifying that a set of trades are to be made, application 104can request that user-level network stack 105 permit packet processingengine 108 to transmit a specified amount of data over a TCP connectionestablished by network stack 105 to an electronic exchange. Theapplication could make such a request by means of software interface 106described in relation to the first invention. FPGA 109 at the NIC canthen operate autonomously, receiving data over network 107 from anelectronic exchange and forming application layer bid and quote messagesin response in accordance with its trading algorithms. Since packetprocessing engine 109 has permission and the necessary state to transmitover the TCP connection to the electronic exchange, the packetprocessing engine can process the application layer messages at the NICand transmit the resulting data packets over the wire at very lowlatency.

The second invention and first invention can be utilised together withthe slave network stack being configured to complete message templatesgenerated by the parent network stack. In fact, the network protocolstate passed from the parent stack to slave stack can be a set of one ormore message templates generated by the parent network stack. Thus, theparent network stack can prepare a set of message templates which arepassed to the slave stack for completion with application layer data andprocessing in accordance with the connection oriented protocol. Theslave network stack can alternatively be configured to form messagetemplates at the NIC in dependence on the state received from the parentnetwork stack, though the slave network stack need not itself besupported at the NIC. The message templates could be stored in memory atthe NIC, or at a memory of a message forming entity supported at the NIC(e.g. at a memory of an FPGA configured to from the application layerdata).

In any of the embodiments of the present invention described herein itis advantageous to configure software interface 106 to provide a “dummy”transmission function that causes the appropriate CPU core of the dataprocessing system to execute a transmit code path without actuallycausing any data to be transmitted over the network. This has the effectof ensuring that the instructions and state required to execute the codepath are resident in the cache of the appropriate CPU core of the dataprocessing system. This is advantageous because the time taken toexecute a particular code path is generally highly dependent on whetherthe instructions that define the code path, and the state touched by thecode path, are resident in the cache of the CPU core executing that codepath. If the instructions and state are not resident in the cache, thecode path typically executes much more slowly.

A dummy transmission function is provided that can be called by asoftware interface so as to cause the appropriate CPU core to, from itspoint of view, perform a transmission operation on the message templatestored at the transmit buffer. In other words, the software interfacecauses the network protocol stack to process the message template inpreparation for transmission by the NIC as though the message templatewere complete. However, the message template is not actually transmittedby the NIC and is preferably not passed to the NIC at all, by PIO or byDMA transfer. The missing portions of the message could be padded withvalues so as to form a “complete” message that can be processed by thestack.

More broadly, a software interface can be configured to provide a dummytransmit function and/or a dummy receive function configured to causethe appropriate CPU core to perform a transmission or receive operation(as appropriate) without actually transmitting or receiving any data atthe data processing system. Such a software interface need not beoperable to form a message template as described above in relation toFIGS. 1 to 3. A dummy transmit function is configured to cause executionof the transmit code path of the appropriate network protocol stack soas to bring the state required by the transmit code path of the networkprotocol stack into the cache of the processor that would perform therespective actual transmit operations. A dummy receive function isconfigured to cause execution of the receive code path of theappropriate network protocol stack so as to bring the state required bythe receive code path of the network protocol stack into the cache ofthe processor that would perform the respective actual receiveoperations. These dummy functions have the effect of ensuring that theinstructions and state required to execute the code path are resident inthe cache of the appropriate CPU core of the data processing system.

Preferably the dummy transmit or receive functions are called by meansof regular transmit or receive functions (such as send( ) or recv( ) TCPsocket calls) carrying a predetermined flag that indicates to thesoftware interface that the transmit/receive function is a dummyfunction. This ensures that calls to the dummy transmit/receivefunctions use the same entry point as regular transmit/receive functioncalls. No payload data need be provided with calls to a dummy transmitfunction, and no payload data need be returned in response to a dummyreceive function. The software interface is preferably a socket API.

Preferably an application is configured to periodically invoke a dummytransmit and/or receive function of the software interface so as toincrease the likelihood that the appropriate instructions and state arein the cache when required by genuine transmit or receive operations.

By providing dummy transmit/receive functions, the software interfaceallows an application to prepare the cache of a CPU and ensure thatlatency of the transmit/receive code paths is minimised.

The applicant hereby discloses in isolation each individual featuredescribed herein and any combination of two or more such features, tothe extent that such features or combinations are capable of beingcarried out based on the present specification as a whole in the lightof the common general knowledge of a person skilled in the art,irrespective of whether s

uch features or combinations of features solve any problems disclosedherein, and

without limitation to the scope of the claims. The applicant indicatesthat aspects of the present invention may consist of any such individualfeature or combination of features. In view of the foregoing descriptionit will be evident to a person skilled in the art that variousmodifications may be made within the scope of the invention.

1. A method of transmitting data for use at a data processing systemsupporting an application, a software interface and a network protocolstack, the data processing system being coupled to a network by anetwork interface device, the method comprising: the application:forming one or more parts of a message for transmission; causing amessage template to be generated by means of a first request to thesoftware interface; the software interface: on receiving the firstrequest, causing the network protocol stack to include said one or moreparts of the message for transmission in the message template and, inaccordance with a predetermined set of protocols, form at least in partone or more protocol headers for the message for transmission; andsubsequently: forming one or more further parts of the message fortransmission; causing the network protocol stack to include the one ormore further parts of the message in the message template and, oncompletion of the message for transmission, process the message inaccordance with the predetermined set of protocols so as to complete theprotocol headers; and causing the network interface device to transmitthe completed message over the network.
 2. A method of transmitting dataas claimed in claim 1, wherein the step of forming one or more furtherparts of the message for transmission is performed by the applicationand the step of causing the network protocol stack to include the one ormore further parts of the message in the message template is effected bymeans of a second request made by the application to the softwareinterface.
 3. A method of transmitting data as claimed in claim 2,wherein the application makes a series of second requests to thesoftware interface, each second request being made on one or morefurther parts of the message for transmission becoming available to theapplication.
 4. A method of transmitting data as claimed in claim 3,wherein the final request of the second request type in the seriescompletes the message for transmission causing the network protocolstack to process the message in accordance with the predetermined set ofprotocols so as to complete the protocol headers and the networkprotocol stack to transmit the completed message.
 5. A method oftransmitting data as claimed in claim 1, wherein the network protocolstack comprises at least two parts: a first part supported at the dataprocessing system and a second part supported at the network interfacedevice; the first part being configured to perform the step of formingat least in part one or more protocol headers of the message fortransmission, and the second part being configured to perform the stepof processing the message so as to complete the protocol headers.
 6. Amethod of transmitting data as claimed in claim 5, wherein the step offorming the one or more further parts of the message for transmission isperformed at a data processing engine of the network interface device.7. A method of transmitting data as claimed in claim 6, wherein the stepof causing the second part of the network protocol stack to process themessage so as to complete the protocol headers is performed in responseto completing formation of the one or more further parts of the messagefor transmission.
 8. A method of transmitting data as claimed in claim5, wherein the first part of the network protocol stack is a user-levelprotocol stack.
 9. A method of transmitting data as claimed in claim 1,wherein at least part of the message template is held at the networkinterface device.
 10. A method of transmitting data as claimed in claim1, wherein the first request includes memory references to the one ormore parts of a message for transmission.
 11. A method of transmittingdata as claimed in claim 1, further comprising, subsequent to thenetwork protocol stack including said one or more parts of the messagefor transmission in the message template, the network protocol stackperforming segmentation of the message template in accordance with apredetermined transport protocol such that the one or more parts of themessage are transmitted over the network in one or more message segmentsby the network interface device.
 12. A method of transmitting data asclaimed in claim 11, further comprising, subsequent to the networkprotocol stack including said one or more further parts of the messagefor transmission in the message template, the network protocol stackcausing those segments of the message template that correspond to thefurther parts of the message for transmission to be transmitted over thenetwork by the network interface device.
 13. A method of transmittingdata as claimed in claim 12, wherein the step of the network protocolstack causing those segments of the message template that correspond tothe further parts of the message for transmission to be transmitted overthe network completes the step of the network interface devicetransmitting the message over the network.
 14. A method of transmittingdata as claimed in claim 11, wherein the predetermined transportprotocol is the transmission control protocol.
 15. A method oftransmitting data as claimed in claim 11, wherein the transport protocolis configured such that a message segment can carry a plurality of partsof the message for transmission that are not contiguous in the messagefor transmission.
 16. A method as claimed in claim 15, wherein a messagesegment can include one or more header fields that determine the logicalposition within the message for transmission of the parts of the messagein the message segment.
 17. A method as claimed in claim 16, wherein theone or more header fields are formed in a TCP header option.
 18. Amethod of transmitting data as claimed in claim 15, wherein all of theone or more parts of the message are transmitted over the network in asingle message segment by the network interface device.
 19. A method oftransmitting data as claimed in claim 1, wherein at least part of themessage template is stored at the network interface device, that part ofthe message template stored at the network interface device includingthe one or more parts of a message for transmission.
 20. A method oftransmitting data as claimed in claim 19, wherein the step of thenetwork protocol stack including the one or more further parts of themessage in the message template comprises transferring the one or morefurther parts of the message into the message template using one or moreprogrammed I/O instructions.
 21. A method of transmitting data asclaimed in claim 19, wherein the step of the network protocol stackincluding the one or more further parts of the message in the messagetemplate comprises: for those further parts of the message that arebelow a predetermined length, transferring the one or more further partsof the message into the message template using one or more programmedI/O instructions; and for those further parts of the message that areabove the predetermined length, transferring the one or more furtherparts of the message into the message template by means of direct memoryaccess by the network interface device.
 22. A method of transmittingdata as claimed in claim 1, wherein the software interface is configuredto provide a dummy transmission function by means of which anapplication can cause the network protocol stack to process the messagetemplate in accordance with the predetermined set of protocols as if fortransmission by the network interface device, the method furthercomprising, prior to the step of the network interface devicetransmitting the message over the network, the application periodicallycalling the dummy transmission function so as to cause the networkprotocol stack to process the message template in accordance with thepredetermined set of protocols without causing the network interfacedevice to transmit the processed message template over the network. 23.A method of transmitting data as claimed in claim 22, wherein the stepof calling the dummy transmission function comprises, prior to thenetwork protocol stack processing the message template in accordancewith the predetermined set of protocols, the network protocol stackpadding the message template with data so as to fill the missing partsof the message for transmission.
 24. A method of transmitting data asclaimed in claim 1, wherein the message template is a logical expressionof the message for transmission.
 25. A method of transmitting data asclaimed in claim 1, wherein the software interface is an applicationprogramming interface.
 26. A method of transmitting data as claimed inclaim 1, wherein at least part of the network protocol stack is at userlevel.
 27. A data processing system coupled to a network by a networkinterface device and comprising: an application configured to form oneor more parts of a message for transmission; a network protocol stackconfigured to process messages for transmission in accordance with apredetermined set of network protocols; a software interface configuredto, in response to a first request, cause the network protocol stack toform at least in part one or more protocol headers of a message fortransmission; wherein the application is configured to, on forming oneor more parts of a message for transmission, make a first request to thesoftware interface so as to cause the network protocol stack to form amessage template comprising at least in part one or more protocolheaders of a message for transmission and the one or more parts of themessage for transmission; and subsequently: the network protocol stackbeing configured to, on one or more further parts of the message fortransmission being formed, include the one or more further parts of themessage in the message template and, on completion of the message fortransmission, process the message in accordance with the predeterminedset of protocols so as to complete the protocol headers and cause thenetwork interface device to transmit the completed message over thenetwork.
 28. A data processing system as claimed in claim 27, whereinthe application is configured to form the one or more further parts ofthe message for transmission and to cause the network protocol stack toinclude the one or more further parts of the message in the messagetemplate by means of a second request to the software interface.
 29. Adata processing system as claimed in claim 27, wherein the one or morefurther parts of the message for transmission are formed at the networkinterface device at a data processing engine of the network interface,and the network protocol stack comprises at least two parts: a firstpart supported at the data processing system and a second part supportedat the network interface device; the first part being configured toperform the step of forming at least in part one or more protocolheaders of the message for transmission, and the second part beingconfigured to perform the step of processing the message so as tocomplete the protocol headers.
 30. A method of transmitting data for useat a data processing system and network interface device, the dataprocessing system being coupled to a network by the network interfacedevice, the method comprising: forming a message template in accordancewith a predetermined set of network protocols, the message templateincluding at least in part one or more protocol headers; forming anapplication layer message in one or more parts; updating the messagetemplate with the parts of the application layer message; processing themessage template in accordance with the predetermined set of networkprotocols so as to complete the protocol headers; and causing thenetwork interface device to transmit the completed message over thenetwork.
 31. A method of transmitting data as claimed in claim 30,wherein the step of forming a message template is performed at a networkprotocol stack supported at the data processing system.
 32. A method oftransmitting data as claimed in claim 30, wherein the step of forming anapplication layer message is performed by one of an applicationsupported at the data processing system, and a data processing engine ofthe network interface device or other peripheral device of the dataprocessing system.
 33. A method of transmitting data as claimed in claim30, wherein the processing step is performed at a packet processingengine supported at the network interface device.
 34. A data processingsystem coupled to a network, the data processing system comprising: anetwork protocol stack configured to, in accordance with a predeterminedset of network protocols, form a message template including at least inpart one or more protocol headers; and a message forming engineconfigured to form an application layer message in one or more partsand, on the formation of each of those parts, cause the respective partof the message to be applied to the message template; wherein thenetwork protocol stack is further configured to, on the applicationlayer message being completed, process the message template inaccordance with the predetermined set of network protocols so as tocomplete the protocol headers and cause the completed message to betransmitted over the network.
 35. A data processing system as claimed inclaim 34, wherein the network protocol stack is supported at a networkinterface device arranged to couple the data processing system to thenetwork.
 36. A data processing system as claimed in claim 34, whereinthe message forming engine is one or both of an application supported atthe data processing system or a data processing engine at a networkinterface device arranged to couple the data processing system to thenetwork.
 37. A method of transmitting data in accordance with aconnection-oriented network protocol, the method being for use at a dataprocessing system coupled to a network and supporting first and secondpacket processing engines, the method comprising: initiating aconnection at the first packet processing engine; the first packetprocessing engine passing first network protocol state to the secondpacket processing engine sufficient to permit the second packetprocessing engine to transmit a specified amount of data over theconnection; forming application layer data for transmission; and thesecond packet processing engine performing packet processing of theapplication layer data in dependence on the first network protocol stateso as to form one or more network messages and causing transmission ofone or more network messages over the connection.
 38. A method oftransmitting data as claimed in claim 37, wherein the data processingsystem is coupled to the network by a network interface device and thesecond packet processing engine is supported at the network interfacedevice.
 39. A method of transmitting data as claimed in claim 37,wherein the step of forming application layer data for transmission isperformed at a data processing engine of the network interface device.40. A method of transmitting data as claimed in claim 37, wherein thestep of forming application layer data for transmission is performed atan application supported at the data processing system.
 41. A method oftransmitting data as claimed in claim 37, wherein the step of formingapplication layer data for transmission is performed at a dataprocessing engine supported at a peripheral device of the system.
 42. Amethod of transmitting data as claimed in claim 37, wherein the passingstep is performed in response to a request made by the second packetprocessing engine.
 43. A method of transmitting data as claimed in claim37, wherein the first network protocol state is a message templateincluding at least in part one or more protocol headers for a networkmessage.
 44. A method of transmitting data as claimed in claim 37,wherein the first packet processing engine performs processing ofnetwork messages received over the connection.
 45. A method oftransmitting data as claimed in claim 37, wherein the first packetprocessing engine is a software network protocol stack supported atkernel or user level at the data processing system.
 46. A method oftransmitting data as claimed in claim 37, wherein the second packetprocessing engine is configured to perform packet processing of theapplication layer data using an FPGA, ASIC, dedicated hardware, orembedded software.
 47. A method of transmitting data as claimed in claim37, further comprising, subsequent to the passing step, the first packetprocessing engine signalling to the second packet processing engine soas to cause the second packet processing engine to return control of theconnection to the first packet processing engine.
 48. A method oftransmitting data as claimed in claim 47, further comprising, inresponse to the signalling, the second packet processing enginecompleting any pending transmission operations over the connection andpassing second network protocol state to the first packet processingengine so as to return control of the connection to the first packetprocessing engine.
 49. A method of transmitting data as claimed in claim37, further comprising, on the amount of data transmitted over theconnection becoming within a predetermined amount of the specifiedamount of data, the second packet processing engine requesting updatednetwork protocol state from the first packet processing engine and, inresponse to the request, the first packet processing engine passingupdated network protocol state to the second packet processing engine.50. A method of transmitting data as claimed in claim 49, furthercomprising: forming additional application layer data for transmission;and the second packet processing engine performing packet processing ofthe additional application layer data in dependence on the updatednetwork protocol state so as to form one or more network messages andcausing transmission of the one or more network messages over theconnection.
 51. A method of transmitting data as claimed in claim 37,wherein the steps of forming the application layer data and performingpacket processing comprise: forming one or more first parts of theapplication layer data; the second packet processing engine processingthe one or more parts of the application layer data in dependence on thefirst network protocol state so as to form a message template includingat least in part one or more protocol headers; and subsequently: formingone or more additional parts of the application layer data; and updatingthe message template with the one or more additional parts of theapplication layer data so as to complete the message template andprocessing the message template so as to complete the protocol headers.52. A method of transmitting data as claimed in claim 37, furthercomprising, once the specified amount of data has been transmitted overthe connection, the second packet processing engine returning control ofthe connection to the first packet processing engine.
 53. A method oftransmitting data as claimed in claim 37, wherein theconnection-oriented network protocol is TCP.
 54. A method as claimed inclaim 37, wherein the data processing engine is an FPGA, ASIC, dedicatedhardware, or embedded software.
 55. A data processing system coupled toa network, the data processing system comprising: a message formingengine operable to form application layer data for transmission over thenetwork in accordance with a connection-oriented network protocol; afirst packet processing engine operable to initiate a connection inaccordance with the connection-oriented network protocol; a secondpacket processing engine operable to perform packet processing ofapplication layer data so as to form one or more network messages inaccordance with the connection-oriented network protocol; wherein thefirst packet processing engine is configured to, subsequent toinitiating the connection, pass first network protocol state to thesecond packet processing engine sufficient to permit the second packetprocessing engine to transmit a specified amount of data over theconnection, and the second packet processing engine is configured to, onreceiving application layer data from the message forming engine,perform packet processing of the application layer data in dependence onthe first network protocol state so as to form one or more networkmessages and cause transmission of one or more network messages over theconnection.
 56. A method for minimising execution latency of acommunication process provided for execution at a data processingsystem, the data processing system being coupled to a network andsupporting a software interface, an application and a network protocolstack providing a communication process, and the method comprising theapplication periodically making a call to a dummy communication functionof the software interface so as to cause the network protocol stack toperform the communication process without communicating data over thenetwork.
 57. A method for minimising execution latency as claimed inclaim 56, wherein the software interface provides a communicationfunction corresponding to the dummy communication function and themethod further comprises the application subsequently making a call tothe communication function in respect of a network message so as tocause the network protocol stack to perform the communication processand communicate the network message over the network.
 58. A method forminimising execution latency as claimed in claim 57, wherein the dummycommunication function and the corresponding communication function areone and the same, and the dummy communication function is identified bymeans of a flag of the communication function.
 59. A method forminimising execution latency as claimed in claim 56, wherein thecommunication process is a transmit process and the step of making acall to a communication function comprises the application periodicallymaking a call to a dummy transmit function of the software interface soas to cause the network protocol stack to perform the transmit processwithout transmitting data over the network.
 60. A method for minimisingexecution latency as claimed in claim 59, wherein the dummy transmitfunction is called in respect of a partial message held at a transmitbuffer of the data processing system.
 61. A method for minimisingexecution latency as claimed in claim 56, wherein the communicationprocess is a receive process and the step of making a call to acommunication function comprises the application periodically making acall to a dummy receive function of the software interface so as tocause the network protocol stack to perform the receive process of thenetwork protocol stack without receiving data over the network.